Automatic storage of electronic receipts across merchants and transaction cards

ABSTRACT

A new approach is proposed that contemplates systems and methods to enable an individual to complete a financial transaction by swiping a magnetic stripe card through a card reader connected to a mobile device. The size of the card reader is miniaturized to be portable for connection with the mobile device. The card reader is configured to reliably read data encoded in a magnetic strip of the card with minimum error in a single swipe and provide a signal that corresponds to the data read to the mobile device, which then decodes the incoming signal from the card reader and acts as a point-of-sale device to complete the financial transaction. Such an approach enables a person to become either a micro-merchant (payee) or a buyer/customer (payer) without having to purchase expensive card reader devices or software.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.12/903,828, filed on Oct. 13, 2010, titled, “SYSTEMS AND METHODS FORDYNAMIC RECEIPT GENERATION WITH ENVIRONMENTAL INFORMATION,” which claimspriority to U.S. Application No. 61/278,930, filed Oct. 13, 2009, titled“Dynamic receipt with environmental information,”; both of which arehereby incorporated by reference herein in their entireties.

This application is related to U.S. patent application Ser. No.12/456,134, filed Jun. 10, 2009, and entitled “Card reader device for acell phone and method of use,” and is hereby incorporated herein byreference.

BACKGROUND

Plastic cards having a magnetic stripe embedded on one side of the cardare prevalent in everyday commerce. These cards are used in varioustransactions such as to pay for purchases by using a credit card, adebit card, or a gasoline charge card. A charge card or a debit card mayalso be used to transact business with a bank through use of anautomated teller machine (ATM). The magnetic stripe card is capable ofstoring data by modifying the magnetism of magnetic particles embeddedin the stripe. The data stored on the magnetic stripe may be sensed orread by swiping the stripe past a read head. The analog waveformobtained by sensing the magnetic stripe must undergo a process known asdecoding to obtain the digital information stored in the magnetic stripeof the card.

Currently, there are hundreds of magnetic stripe readers/swipers on themarket, all of them are at least as long as the credit card itself.These existing readers/swipers can be classified as either platform cardreaders or plunge card readers. Platform card readers are traditionalcard swipers with single rails, which allow a card to be held againstthe base of the reader by the user and moved across the read head of thereader. Plunge swipers guide a card by two sets of rails and a backstop.Once the user has inserted the card against the backstop, the card isread as it is removed from the plunge swipers. Plunge swipers are commonon ATMs and other self-pay devices because they are less prone tohacking.

Magnetic stripe cards having standard specifications can typically beread by point-of-sale devices at a merchant's location. When the card isswiped through an electronic card reader, such as a platform cardreader, at the checkout counter at a merchant's store, the reader willusually use its built-in modem to dial the number of a company thathandles credit authentication requests. Once the account is verified andan approval signal will be sent back to the merchant to complete atransaction.

Although magnetic stripe cards are universally used by merchants, thereis no way for an individual to take advantage of the card to receive apayment from another individual (who is not a merchant) by swiping thecard through a simple reader attached to his/her mobile device. For anon-limiting example, one person may owe another person money for adebt, and the conventional way to pay the debt is to provide cash or acheck. It would be convenient to be able to use a credit card or a debitcard to payoff the debt. In addition, it is advantageous for anindividual to make payment to another individual or merchant by swipinghis magnetic stripe card through a reader connected to a mobile device.

The foregoing examples of the related art and limitations relatedtherewith are intended to be illustrative and not exclusive. Otherlimitations of the related art will become apparent upon a reading ofthe specification and a study of the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an example of a system diagram to support financialtransaction between a payer and a payee through a miniaturized cardreader connected to a mobile device.

FIG. 2 depicts an example of an external structural diagram of aminiaturized card reader.

FIGS. 3A-3B depict examples of actual card reader with miniaturizeddesign.

FIGS. 4A-4B depict examples of alignment between read head of the cardreader and magnetic stripe of card being swiped.

FIG. 5 depicts an example of a TRS connector as a part of card reader.

FIGS. 6A-C depict examples of internal structures of a miniaturized cardreader.

FIGS. 7A-B depict examples of waveforms of data read from one track ofthe magnetic stripe by read head when the card is swiped through theslot of the card reader in the forward and reverse directions,respectively.

FIG. 8 depicts a flowchart of an example of a process to support swipingof a card with a magnetic stripe through a miniaturized portable cardreader.

FIG. 9 depicts an example of schematic diagram of passive ID circuitryembedded in the card reader.

FIG. 10 depicts an example of schematic diagram that contains additionalcomponents of passive ID circuitry 22 that contribute to the userexperience.

FIG. 11 depicts an example of an implementation for passive ID circuitry22 depicted in FIG. 10.

FIG. 12 depicts a flowchart of an example of a process to deliver theunique ID to mobile device via the passive ID circuitry.

FIG. 13 depicts an example of additional encryption and/or decryptionsystems included in the passive ID circuitry for encrypting anddecrypting of unique ID of card reader.

FIG. 14 depicts a flowchart of an example of a process to supportdecoding of incoming signals from swiping of a card with a magneticstripe through a miniaturized portable card reader.

FIG. 15 depicts a flowchart of an example of a process to supportfinancial transaction between a payer and a payee through a miniaturizedcard reader connected to a mobile device.

FIGS. 16A-F depict screenshots of an example of a financial transactionbetween a purchaser and a merchant through a miniaturized card readerconnected to a mobile device.

DETAILED DESCRIPTION OF EMBODIMENTS

The approach is illustrated by way of example and not by way oflimitation in the figures of the accompanying drawings in which likereferences indicate similar elements. It should be noted that referencesto “an” or “one” or “some” embodiment(s) in this disclosure are notnecessarily to the same embodiment, and such references mean at leastone.

A new approach is proposed that contemplates systems and methods toenable an individual to complete a financial transaction by swiping amagnetic stripe card through a card reader connected to a mobile device.Here, the financial transaction can be any transaction that involvesreceiving or sending payment from one person to another. The magneticstripe card can be but is not limited to a credit card, a debit card, orother types of payment authenticating pieces capable of carrying out thefinancial transaction. The size of the card reader is miniaturized to beportable for connection with the mobile device. The card reader isconfigured to reliably read data encoded in a magnetic strip of the cardwith minimum error in a single swipe and provide a signal thatcorresponds to the data read to the mobile device, which then decodesthe incoming signal from the card reader and acts as a point-of-saledevice to complete the financial transaction. Such an approach enables aperson to become either a micro-merchant (payee) or a buyer/customer(payer) without having to purchase expensive card reader devices orsoftware.

FIG. 1 depicts an example of a system diagram to support financialtransaction between a payer and a payee through a miniaturized cardreader connected to a mobile device. Although the diagrams depictcomponents as functionally separate, such depiction is merely forillustrative purposes. It will be apparent that the components portrayedin this figure can be arbitrarily combined or divided into separatesoftware, firmware and/or hardware components. Furthermore, it will alsobe apparent that such components, regardless of how they are combined ordivided, can execute on the same host or multiple hosts, and whereinmultiple hosts can be connected by one or more networks.

In the example of FIG. 1, the system includes a mobile device 100, aminiaturized card reader 10 connected to mobile device 100, a decodingengine 110, a user interaction engine 120, and a transaction engine 130,all running on mobile device 100. Additionally, the system may alsoinclude one or more of user database 140, product or service database150, and transaction database 160, all coupled to the transaction engine130.

As used herein, the term engine refers to software, firmware, hardware,or other component that is used to effectuate a purpose. The engine willtypically include software instructions that are stored in non-volatilememory (also referred to as secondary memory). When the softwareinstructions are executed, at least a subset of the softwareinstructions is loaded into memory (also referred to as primary memory)by a processor. The processor then executes the software instructions inmemory. The processor may be a shared processor, a dedicated processor,or a combination of shared or dedicated processors. A typical programwill include calls to hardware components (such as I/O devices), whichtypically requires the execution of drivers. The drivers may or may notbe considered part of the engine, but the distinction is not critical.

As used herein, the term database is used broadly to include any knownor convenient means for storing data, whether centralized ordistributed, relational or otherwise.

In the example of FIG. 1, mobile device 100, to which the portable cardreader 10 is connected to, can be, but is not limited to, a cell phone,such as Apple's iPhone® (mobile digital device), other portableelectronic devices, such as Apple's iPod Touches® (mobile digitaldevice), Apple's iPads® (mobile digital devices), and mobile devicesbased on Google's Android™ operating system, and any other portableelectronic device that includes software, firmware, hardware, or acombination thereof that is capable of at least receiving the signal,decoding if needed, exchanging information with a transaction server toverify the buyer and/or seller's account information, conducting thetransaction, and generating a receipt. Typical components of mobiledevice 100 may include but are not limited to persistent memories likeflash ROM, random access memory like SRAM, a camera, a battery, LCDdriver, a display, a cellular antenna, a speaker, a Bluetooth® circuit,and WIFI circuitry, where the persistent memory may contain programs,applications, and/or an operating system for the mobile device.

Miniaturized Card Reader

In the example of FIG. 1, miniaturized card reader 10 is configured toread data encoded in a magnetic strip of a card being swiped by a buyerand send a signal that corresponds to the data read to mobile device 100via a signal plug 18. The size of card reader 10 miniaturized to beportable for connection with mobile device 100. For a non-limitingexample, the size of card reader 10 can be miniaturized to an overalllength of less than 1.5″. In addition, the miniaturized card reader 10is also designed to reliably read the card with minimum error via asingle swipe by counteracting vendor specific filtering done by mobiledevice 100. Note that this broad overview is meant to be non-limiting ascomponents to this process are represented in different embodiments. Forinstance the decoding engine 110 can be embedded in the card reader 10as shown in FIG. 13 as the decoding system 42. FIG. 2 depicts an exampleof an external structural diagram of miniaturized card reader 10.Although the diagrams depict components as functionally separate, suchdepiction is merely for illustrative purposes. It will be apparent thatthe components portrayed in this figure can be arbitrarily combined ordivided into separate software, firmware and/or hardware components.

In the example of FIG. 2, miniaturized card reader 10 is shown tocomprise at least a housing 12 having a slot 14, a read head 16 embeddedon a wall of slot 14, a signal plug 18 extending out from the housing12, and an optional passive ID circuit 22. FIG. 3A depicts an example ofan actual card reader with miniaturized design and FIG. 3B depicts otherexamples of miniaturized card reader with width around 0.5″.

In the example of FIG. 2, housing 12 of card reader 10 is designed to beasymmetrical with respect to slot 14, with texture such as logo on oneside of the housing that can be felt and recognized by a user with atouch of a finger. For correct swiping of the card, the texture side ofhousing 12 should match with the texture (front) side of the card, sothat a user can easily identify the right side of the reader to swipethe card through slot 14 without actually looking at the reader or card.Even a blind person is able to swipe the card correctly by matching thetexture side of the reader with the texture side of the card.

In the example of FIG. 2, the slot 14 is wide enough and deep enough toaccept a card having a magnetic stripe so that the stripe will fitwithin the slot 14. More importantly, the slot 14 is configured toreduce the torque applied on the reader 10 when the card is swipedthrough slot 14 in order to maintain accuracy and reliability of thedata read by read head 16. Since the size of card reader 10 isminiaturized, slot 14 also has a length that is significantly less thanthe length of the card to be inserted into the slot 14.

To correctly read the data on the magnetic stripe of the card, the readhead 14 must maintain contact with the stripe as the card moves pastslot 14. If the card rocks during the swipe, the alignment of the head12 with the stripe may be compromised. As the length of the slot 14,i.e., the card path through which the card swiped though slot 14, isshortened, rocking and head alignment may become significant issues. Asshown in FIG. 4A, if the magnetic stripe card is swiped through withoutthe base of the card resting against the flat bottom piece, the magneticstripe will not align with the read head 16 when the card is swipedthrough slot 14 having a flat base 15.

In some embodiments, the base 15 of slot 14 can be changed from flat toa curved base with a radius in order to increase contact between theread head 14 and the magnetic stripe to address the rocking problem. Asshown in FIG. 4B, the read head 16 can maintain contact with themagnetic stripe, even with some additional error due to the gradation ofcontact introduced by the curved base 15.

FIG. 5 depicts an example of signal plug 18 as part of card reader 10.Here, signal plug 18 can be but is not limited to a TRS (tip, ring,sleeve) connector also known as an audio plug, phone plug, plug plug,stereo plug, mini-plug, or a mini-stereo audio connector. The signalplug 18 may be formed of different sizes such as miniaturized versionsthat are 3.5 mm or 2.5 mm.

In some embodiments, signal plug 18 may be retractable within thehousing 12. In some embodiments, signal plug 18 is configured to extendbeyond housing 12 of the reader in order to accommodate connection withmobile devices 100 having cases or having a recessed plug-in socket,wherein the socket can be but is not limited to a microphone inputsocket or a line in audio input of the mobile device.

In some embodiments, housing 12 of card reader 10 is made ofnonconductive material such as plastic so that the reader will notinterfere with the function of mobile device 100 it is connected with.Such choice of material is important since the outer case of certainmobile devices, such as iPhone® 4, is conductive and serves as anantenna for the device, which function could potentially be interferedwith if the metal case of the device gets in touch with the housing of acard reader made of conductive material.

FIG. 6A depicts an example of an internal structural diagram of aminiaturized card reader. Although the diagrams depict components asfunctionally separate, such depiction is merely for illustrativepurposes. It will be apparent that the components portrayed in thisfigure can be arbitrarily combined or divided into separate software,firmware and/or hardware components.

In the example of FIG. 6A, the internal structure inside housing 12 ofcard reader 10 is shown to comprise at least a read head 16 withembedded circuitry, and a spring structure 20 to support read head 16.FIG. 6B depicts an example of an internal structure an actualminiaturized card reader. FIG. 6C depicts an example of separatedcomponents of read head 16 and spring structure 20 used in the actualminiaturized card reader.

In the example of FIGS. 6A-C, read head 16, which for a non-limitingexample, can be an inductive pickup head, detects and provides datastored in the magnetic stripe of a card to a connected mobile device100. More specifically, as the magnetic stripe of a card is swipedthrough slot 14 and in contact with read head 16, the card reader device10 reads one or more tracks of data or information stored in themagnetic stripe of the card via the detection circuitry embedded insidethe read head. Here, data stored in the magnetic stripe may be in theform of magnetic transitions as described in the ISO 7811 standards. Asthe card moves past the read head 16, magnetic transitions representingdata induce a voltage or waveform in a coil (not shown) of read head 16due to such relative movement between read head 16 and the stripe(called the Hall Effect), wherein a resistor (not shown) inside readhead 16 sets the amplitude of the waveform. This waveform is sent viathe signal plug 18 into the socket which is registered by the microphoneof the mobile device 100 connected with card reader 10.

In some embodiments, read head 16 in card reader is capable of readingonly one track of data (either track 1 or 2, but not both) from themagnetic stripe in order to reduce the size and structural complexity ofcompact read head 16 as only one pin needs to be included in the readhead. FIGS. 7AB depict examples of waveforms of data read from track 1(instead of both tracks 1 and 2 as by a traditional read head) of themagnetic stripe by read head 16 when the card is swiped through slot 14in the forward and reverse directions, respectively.

In some embodiments, the size or thickness of the housing 12 of cardreader 10 is configured to be narrow enough to accommodate only a singleread head 16. Such design is intended to be tampering-proof so that evenif the housing 12 is tampered with, no additional circuitry can be addedto the card reader 10 and such tampering will render the card readernon-functional.

In the example of FIGS. 6A-C, spring structure 20 is a flexible springmounting to read head 16 without a screw, causing the read head to besuspended to housing 12 of card reader 10. Here, spring 20 can either beconnected to housing 12 via screws or welded to plastic housing 12without using any screws. As the card moves past the read-head 16 on theminiaturized card reader, any card bending or misalignment may cause theread head to lose contact with the magnetic stripe. Spring 20 allowssuspended read head 16 to swivel while maintaining contact pressure totrack the stripe of the card being swiped. Spring 20 is designed to besufficiently small to fit within the miniaturized card reader 10, yetpowerful enough to maintain good contact during the stripe. Unliketraditional spring structures, spring 20 positions the supports for readhead 20 inside the overall form of the spring, which allows the springto flex without having to make one support moveable.

FIG. 8 depicts a flowchart of an example of a process to support swipingof a card with a magnetic stripe through a miniaturized portable cardreader. Although this figure depicts functional steps in a particularorder for purposes of illustration, the process is not limited to anyparticular order or arrangement of steps. One skilled in the relevantart will appreciate that the various steps portrayed in this figurecould be omitted, rearranged, combined and/or adapted in various ways.

In the example of FIG. 8, the flowchart 800 starts at block 802 where aminiaturized card reader is structured to provide sufficient contactbetween a read head and the magnetic stripe during a swipe of a card.The flowchart 800 continues to block 804 where a card with a magneticstripe is swiped through a slot of the miniaturized card reader. Theflowchart 800 continues to block 806 where the read head reliably readsdata stored in the magnetic stripe and generates an analog signal orwaveform indicative of data stored in the magnetic stripe. The flowchart800 continues to block 808 where amplitude of the waveform is set by thecircuitry inside the read head. The flowchart 800 ends at block 810where the set waveform is provided to a mobile device 100 connected withthe miniaturized card reader via the signal plug 18.

Passive ID Circuit

In some embodiments, housing 12 of card reader 10 may furtherencapsulate a passive ID circuitry 22 powered by the mobile device 100through signal plug 18, wherein passive ID circuitry 22 delivers anunique ID of the card reader to mobile device 100 only once upon thecard reader being connected to (and powered up by) the mobile device.Although both are integrated in the same housing 12, passive IDcircuitry 22 functions independently and separately from read head 18without interfering with the read head's card swiping functionsdescribed above.

FIG. 9 depicts an example of schematic diagram of passive ID circuitryembedded in the card reader. In the example of FIG. 9, passive IDcircuitry 22 may comprise at least five main subsystem/components:unique ID storage 24, communication subsystem 26, which reads andtransmits the unique ID from unique ID storage 24, power subsystem 28,which provides power to enable communication with mobile device 100, apathway subsystem 30 to route signals to signal plug 18 through thecircuitry, and a control unit 32, to orchestrate the communicationbetween different systems. All of these subsystems can be implemented inhardware, software or a combination thereof. Communication subsystem 26,power subsystem 28, and read head 16 share the same signal plug 18 forconnection with the mobile device. The components portrayed in thisfigure can be arbitrarily combined or divided into separate software,firmware and/or hardware components.

In the example of FIG. 9, unique ID storage 24 is memory containing theUnique ID of the card reader. The unique ID storage 24 can be anypersistent memory containing bytes that can be accessed by thecommunication subsystem 26.

In the example of FIG. 9, the power subsystem 28 comprises of a modifiedcharge pump, which utilizes a digital circuit to artificially raise thevoltage of a power source to a higher level. Normal charge pumpoperation requires large current which is then fed into severalcapacitors, and switching logic switches the capacitors between seriesand parallel configurations. In the example of FIG. 10, the power sourceis a bias voltage provided by the mobile device meant for detection of aconnected component. It is nominally 1.5V and is supplied through a 21 d2 resistor, resulting in a maximum current of 750 μA. Details of how thepower subsystem 28 function is described in FIG. 11.

In standard operation the pathway subsystem 30 is configured to directthe mobile device's 100 bias voltage to the power subsystem 28. Afterthe power subsystem converts the bias voltage to a system voltage, thecontrol unit 32 is able to operate. Control unit 32 configures thepathway subsystem 30 to allow the communication subsystem 26 access tothe mobile device 100. The communication subsystem 26 relays the uniqueID from the unique ID storage 24. The control unit 32 then configuresthe pathway subsystem 30 to allow the card reader circuit 16 access tothe mobile device 100.

FIG. 10 depicts an example of schematic diagram that contains additionalcomponents of passive ID circuitry 22 that contribute to the userexperience. These additional systems prevent the mobile device 100 fromperceiving that the card reader 10 has been disconnected during powercycles. These additional systems also ensure that the unique ID sentfrom unique ID storage 24 is sent as specified by the designer. Thisextra feature set comprises of a discharge subsystem 34 to force thedevice to power cycle, a fake load 36 so the mobile device 100 does notperceive a disconnect, and a monitor system 38 to manage card reader 10behavior between power cycles.

In the example of FIG. 10, communication subsystem 26 comprises a signaldriver connected with control unit 32 and unique ID storage 24. In anon-limiting embodiment of a system which sends an 10 only once to amobile device 100, after the control unit 32 boots up, communicationsubsystem 26 will check a status bit in the monitor subsystem 38. Thefirst time this process occurs, the status bit will be not set. When thestatus bit is not set the 10 is sent immediately. FIG. 12 contains adetailed flowchart of a non-limiting example of this process. In oneembodiment the control unit 32 will write to the status bit in monitorsubsystem 38. It will then use the discharge system 34 to reset itself.During this time the pathway subsystem 30 will be configured to directthe signal path to the fake load preventing the mobile device 100 fromdetecting a disconnect with the card reader 10. Once the power subsystem28 has completed its power cycle, the control unit 32 will read thestatus bit. Upon seeing that the status bit is cleared it will configurethe pathway subsystem 30 to direct the signal path to the card readercircuit 16. The control unit 32 will then put the system into anextremely low power state (from here referred to as a sleep state). Onlythe monitoring subsystem 38 will remain active. The monitor subsystem 38will wake the system from the sleep state at some time (time dependingon implementation) before a power cycle. The control unit 32 willnotified of the system awakening by the monitoring subsystem 38. Thecontrol unit 32 will then set the status bit on the monitor subsystem 38only if there is a voltage detected on the fake load indicating thereader is still connected. The control unit 32 will then force a powercycle.

FIG. 11 depicts an example of an implementation for passive ID circuitry22 depicted in FIG. 10. In some embodiments, power subsystem 28 hasmultiple capacitors in parallel. A voltage breaker (e.g., zener diodeetc) and a latch are used to trigger the transition between parallel andseries configurations. Once the latch is flipped, power subsystem 28will remain in series configuration until the combined voltage dropsbelow the CMOS trigger gate voltage, at about 4V. At this time thepassive ID circuitry 22 will reset and the unique ID delivery processwill begin again

In the example of FIG. 11, pathway subsystem 30 comprises a plurality oflatches controlled by control unit 32 for switching among varioussubsystems of passive 10 circuitry 22. When passive ID circuitry 22 isin operation, the default configuration allocates the output signalthrough signal plug 18 to modified charge pump of power subsystem 28.After the latch to turn off modified charge pump 28 is triggered,control unit 32 will route signal plug 18 from read head 16 tocommunication subsystem 26 and transmit the unique ID through signalplug 18 after checking the status bit in unique ID storage 24. Pathwaysubsystem 30 will then write to the status bit in unique ID storage 24and discharge the power subsystem 28. FIG. 12 depicts a flowchart of anexample of a process to deliver the unique ID to mobile device 100 viathe passive ID circuitry 22.

In some embodiments, passive ID circuitry 22 may further includeadditional encryption and/or decryption systems as shown in FIG. 13 forencrypting and decrypting of unique ID of card reader 10. In the exampleof FIG. 13, the decoding system 42 and encryption system 40 can both usethe control unit 32 from the passive ID circuitry 22 to communicate withthe mobile device 100 over the communication subsystem 26.

Signal Decoding

Once card reader 10 provides the set waveform to the attached mobiledevice 100, the incoming signals (waveform) may be amplified, sampled,and converted to a stream of digital values or samples by decodingengine 110 running via a microprocessor inside the mobile device. Here,decoding engine 110 may comprise a pipeline of software decodingprocesses (decoders) to decode and process the incoming signals asdescribed below, where each software process in this pipeline can beswapped out and replaced to accommodate various densities of track dataread in order to reduce card swipe error rate. The incoming signals maybe of low quality due to one or more of: low quality of data read from asingle and/or low density track of a magnetic stripe of the card,sampling speed limitations of the microphone input socket of the mobiledevice, and noise introduced into the mobile device 100 from card reader10. FIG. 14 depicts a flowchart of an example of a process to supportdecoding of incoming signals from swiping of a card with a magneticstripe through a miniaturized portable card reader.

In the example of FIG. 14, the flowchart 1400 starts at block 1402 wheredecoding engine 110 initializes its internal state by waiting for thesystem voltage to reach a steady state. Upon initial connection of acard reader, there is usually a burst of signal due to feedback causedby slight impedance mismatches and the presence of non-linear elementslike the read head. After at least 3 time constants, the signal isdetermined to be in a steady state. During such initialization phase,the DC offset of the incoming signals are computed when the mobiledevice is first connected to the card reader over signal plug 18. Insome embodiments, initialization goes through at least the followingsteps:

1. Take one system buffer of audio signal and compute the DC offset ofthis buffer.

2. Save the computed DC offset.

3. Compute the average of the last three DC offsets.

4. Compute the variance of the current DC offset from the averagecomputed in step 3.

The following values presented were found to be optimum for performancein the decoding system. In the spirit of full disclosure they have beenprovided here to allow someone trained in the arts to be able toreplicate this process. It is fully realized that many other values canbe used here and depending on hardware implementation. The values hereare meant to be non-limiting. If the variance computed in step 4 is lessthan the variance threshold, 0.06% of full scale or less than the offsetpercentage, 10% of the offset average computed in step 3, and the DCoffset computed in step 1 is less than the noise ceiling, 3% of fullscale, of the mobile device 100. After initialization is complete,decoding engine 110 can proceed to process the incoming signals todetect the swipe of the card. Otherwise, Steps 1-4 need to be repeated.

The flowchart 1400 continues to block 1404 where decoding engine 110detects the card swipe once the incoming signals are in a steady state.This signal detection phase processes the incoming signals in steadystate in order to detect the presence of a swipe of a card through thecard reader. The signal detection phase is a light-weight procedure thatoperates at near real time. It parses the incoming signals quickly andstitches multiple system buffers of signals together to form a signalof⋅interest. In some embodiments, the signal detection process goesthrough at least the following steps:

-   -   1. Apply a software upscale of system buffers of the incoming        signals.    -   2. Begin taking buffers of incoming signals and look for points        that exceed a minimum signal amplitude threshold, which is a        hardware-based parameterization found empirically.    -   3. Set a flag that triggers the detection of a swipe once a        single point that exceeds the threshold is detected.    -   4. Once the flag triggered, the incoming signal is appended to a        larger buffer until the signal drops below a minimum signal        amplitude threshold for a certain period of time, e.g., 10 ms.    -   5. Trim the last 10 ms of data to reduce the amount of signal        data to be processed later.    -   6. Check to see if at least a certain number of samples have        been collected in the buffer to make sure that there are enough        information for later decoding. This number is parameterized        based on the hardware of the mobile device used.

Alternatively, a hardware independent swipe detection process can beutilized to capture the signal of interest via Fast Fourier Transform(FFT), while trimming the front and back of the signal. Such processwould include at least the following steps:

-   -   1. Retrieve system buffers of incoming signals and keep a        certain number of buffers of history of the signals.    -   2. Compute the frequency distribution of the signal history kept        via FFT.    -   3. Locate two maxima in the histogram and check if one maximum        is located at 2 x the frequency of the other maximum. If this        condition is satisfied, continue to add on buffers of history        that exhibit such behavior.    -   4. Once such behavior has stopped, begin removing signals from        the beginning and ending of the signals in the buffers until SNR        is maximized, wherein SNR is defined to be the two maxima's        amplitudes that are greatest from the next maximum.

The flowchart 1400 continues to block 1406 once a card swipe is detectedto be present where decoding engine 110 identifies peaks in the incomingsignals. Peak detection is the most complex portion of decoding ofincoming signals from credit card swipes, and credit card swipe decodeshave traditionally not been done on heavily filtered signals like thesignal that enters through the TRS plug, since most mobile devicemanufacturers assume the incoming signal is audio based. This results ina wide variety of signal filtering that peak detection must account for.Different peak detection approaches discussed below can be utilized bythe microprocessor to perform peak detection in the incoming signals indifferent ways, all applying a basic, moving average low-pass filter tosmooth out some of the high frequency noise in order to overcome the lowquality data read, sampling speed limitations of the mobile device, andthe noise introduced into the mobile device.

Reactive Peak Detection

Reactive peak detection is a heuristics based approach for peakdetection, which is well suited for situations where the incomingsignals from the card swipe is not excessively distorted by the mobiledevice's filter circuitry. This approach utilizes at least the followingsteps to detect signal peaks:

-   -   1. Seed an adaptive positive and adaptive negative threshold        with an ambient noise value that is dependent on the hardware of        the mobile device. These thresholds will be used for initial        peak detection.    -   2. Begin processing through the sample buffer, and for each        sample in the buffer:    -   3. Wait for the threshold to be crossed again when either the        negative or positive threshold is crossed, except with a        hysteresis factor applied to the threshold for the second        crossing. The hysteresis factor is key in making this approach        resistant to ringing in the incoming signals, which is        associated with the active filter(s) of the platform hardware.    -   4. Begin looking for slope changes within this time frame once        the two samples where the threshold is crossed have been        established.    -   5. If more than one slope change is found, compute the midpoint        of the two samples.    -   6. If only a single slope change is detected, then        -   a. Pick the maximum point for the slope change.        -   b. Compare the peak's amplitude to the previously found            peak's amplitude (if this has been established).        -   c. Skip the current peak and move on if its amplitude is            greater than (([full scale]−[current peak amplitude])/([full            scale] *100)+100) % of the previous peak's amplitude.    -   7. If the prior step did not result in skipping of the peak,        check the peak's polarity against the previous peak's polarity.        -   a. If the peak's polarity is the same as the previous peak's            polarity, then remove the previous peak and put the current            peak in its place.        -   b. If the polarity of the current peak has changed, then            simply add the current peak to the list of peaks. This step            is another key component for making this approach resistant            to ringing.    -   8. Upon the finding of a peak, update the adaptive threshold of        the corresponding polarity as the polarity of the peak just        found and the amplitude to be a percentage of this peak's        amplitude. Here, the percentage is a parameter varied by the        detection approach being used, since higher values more        accurately detects peaks, but are not as resistant to noise,        while lower values are more resistant to noise, but may pick up        errant peaks associated with ringing.

Predictive Peak Detection

Predictive peak detection defers the heavy processing to the digitizingstage of decoding. Predictive peak detection is highly resistant toscratches in the card that could cause low quality or false peakinformation to manifest in the incoming signals. This approach is morememory intensive than the reactive peak detection approach since morepeaks are stored. The approach utilizes at least the following steps todetect signal peaks:

-   -   1. Seed a positive and adaptive negative threshold with an        ambient noise value that is dependent on the hardware of the        mobile device.    -   2. Begin going through the sample buffer. For each sample in the        buffer:    -   3. Begin waiting for the slope to change when either the        positive of negative threshold is crossed.    -   4. When the slope changes, store the current sample as a peak.

Maxima Peak Detection

Maxima peak detection detects peaks by looking for local maxima andminima within a window of digital samples. If either of these is at theedges of the window of samples, then the approach skips the window andmoves to the next window to look for local maxima and minima. Theselocal maxima and minima are then stored into a list of peaks.

The flowchart 1400 continues to block 1408 where decoding engine 110identifies the track from which data of the incoming signals are readthrough the swipe of the card via the card reader. Traditionally, track1 and track 2 came off of different pins on the read head of a cardreader, and so there was no need to guess which track is being read.Since read head 16 in card reader is capable of reading only one trackof data from the magnetic stripe, track identification becomes animportant issue. This track identification process is run by detectionengine 110 after peaks are detected to guess and recognize the track(track 1 or track 2) from which the data is read by card reader byinferring a range of peaks to be expected for signals coming from eachtrack. Since track 1 is known to be much denser in data than track 2, itis thus reasonable to expect more peaks to be identified in data comingfrom track 1. Although this process is not a definitive guess, it yieldsthe correct track value 99.9% when coupled with the peak detectionalgorithms described herein in testing. Alternatively, track guessingcan be based on the number of bits found in the digital signals afterthe digitizing stage of decoding. When a decoder fails due to guessingthe wrong track (since track identification affects how the bits fromthe digital signals are framed and matched against character sets), thedecoder may simply choose another track type, though this makes the cardprocessing more processor intensive.

The flowchart 1400 continues to block 1410 where decoding engine 110digitizes the identified peaks in the incoming signals into bits. Thedigitizing process takes the given peak information turns them intobinary data and appends them to an array of digital bits. There are twotypes of digitizers: reactive digitizing and predictive digitizing.

Reactive Digitizing

Reactive digitizing takes the given peak information as fact, andattempts to convert them into 1 s and 0s in the following steps:

-   -   1. Go through all peak information. For each peak:    -   2. Identify the distance between each pair of adjacent peaks.    -   3. If these distances are similar (e.g., based on a parameter        for finding a series of peaks that are equidistant from each        other), begin looking for 1s and 0s. The initial peaks always        represent zeros, since the credit card is padded with zeros at        the front and back of the signal.    -   4. Once equidistant peaks are found, identify the number of        samples between peaks, which is the number of samples that        roughly equate to a bit.    -   5. Examine the number of samples between the current peak and        the next peak.    -   6. Examine the number of samples between the current peak and        the peak after the next.    -   7. Compare the results from Steps 5 and 6 against the value from        Step 4:        -   a. If the result from Step 5 is closer to the value from            Step 4, then identify the bit found as a 0.        -   b. If the result from Step 6 is closer, then identify the            bit found as a 1.        -   c. Tie breaking: if the distances are equal and the next two            peak amplitudes are smaller than the current peak amplitude,            then identify the bit found as a 1. Otherwise, identify the            bit found as a 0.    -   8. Once the peak is determined, update the bit length based on        the peak found: if the peak found was a 0, update with the value        of Step 5; otherwise, use the value of step 6.

Predictive Digitizing

Predictive digitizing of detected peaks in the incoming signals does nottreat the list of peaks as facts. It first finds bit length, and thenseeks to a point in the peak list where the next relevant peak shouldbe. Once it reaches this location, it then searches before and after thelocation for the nearest peak. The process then checks the polarity ofthis peak compared to the previous peak examined. If the polarities arethe same, the bit found is identified as a 1. Otherwise, it isidentified as a 0. This method of digitizing a peak list is effective inthat it simply ignores any information that is likely irrelevant.

The flowchart 1400 ends at block 1412 where decoding engine 110 convertsthe array of digitized bits into words of card information. Thisconverting process locates the bit sequence that is the start sentinelin the array. At that point, it takes frames of bits (e.g., 5 bits fortrack 2, 7 bits for track 1) and decodes them based on a symbol table.Along the way, the process constantly checks for parity and the LRC atthe end to ensure the data is correct. If there are any errors inparity, LRC, or track length, blocks 1406-1412 may be repeated with adifferent set of parameters to get the correct signal data.

When a card swipe begins, decoding engine 110 can combine various peakdetectors and digitizers discussed above in order to cover variousranges of degradation in quality of the analog input signal generated bycard reader 10. In some embodiments, different process combinations andparameters can be chosen and optimized depending on the hardwareplatform of the mobile device. These combinations and parameter valuescan be pre-determined based on experimentation and testing andinitialized upon starting of the decoding process. The decoding thenruns through all processes specified and runs certain specific processesmultiple times in order to get the correct signal. Such decoding processallows automatic scaling and adjustment during each run to account fordifferent amounts of noise, sampling speed variations, signal ringing,and swipe direction.

Card Present Transaction without Information Sharing

In the example of FIG. 1, user interaction engine 120 is a softwareapplication running on mobile device 100 associated with a payee(merchant) that enables the payer (buyer) and the merchant to interactwith transaction engine 130 to complete a financial transaction. Morespecifically, it may take input of information related to the financialtransaction from the buyer and/or the merchant, provide such input totransaction engine to initiate and complete the transaction, and presentthe result of the transaction to the buyer and the merchant. Here, theinput of information accepted by user interaction engine 120 may includebut is not limited to one or more of: amount of the transaction,including list price and optionally tips, additional notes related tothe transaction such as written description and/or pictures of the itemto be purchased, authorization and/or signature of the buyer.

In some embodiments, other than the conventional keyboard, userinteraction engine 120 may utilize a touch screen of mobile device 100to enable the buyer and the merchant to input numbers, characters, andsignatures by touching the screen via a stylus or a finger.

In some embodiments, in addition to the result of the transaction, userinteraction engine 120 may also present products or services provided bythe merchant to the buyer in combination of one or more of text,pictures, audio, and videos, and enable the buyer to browse through theproducts and services on the mobile device to choose the one he/sheintended to purchase. Such product information can be stored and managedin product database 150.

In the example of FIG. 1, transaction engine 130 takes as its input thedecoded credit card information from decoding engine 110 and transactionamount from user interaction engine 120. Transaction engine 130 thencontacts third party financial institutions such as an acquiring bankthat handles such authorization request, which may then communicate withthe card issuing bank to either authorize or deny the transaction. Ifthe third party authorizes the transaction, then transaction engine 130will transfer the amount of money deducted from the account of the cardholder (e.g., the buyer) to an account of the merchant and provide thetransaction results to user interaction engine 120 for presentation tothe buyer and the merchant. In this manner, the merchant may accept apayment from the buyer via card reader 10 and mobile device 100.

In the example of FIG. 1, although mobile device 100 is associated withthe merchant, transaction engine 130 running on mobile device 100protects the privacy of the buyer/payer during the card-presenttransaction by taking card information from the buyer directly fromdecoding engine 110 and do not share such information with the merchantvia user interaction engine 120. Here, the card information that are notshared with the merchant includes but is not limited to, card number,card holder's name, expiration date, security code, etc. In essence,transaction engine 130 serves as an intermediary between the buyer andthe merchant, so that the buyer does not have to share his/her cardinformation with the merchant as in a typical card-present transactionor an online transaction. Still, the buyer is able obtain an itemizedreceipt for the transaction completed as discussed later.

In some embodiments, although transaction engine 130 does not share cardinformation of the buyer to the merchant, it may present identityinformation of the buyer, such as a picture of the buyer on record inuser database 140, with the merchant via user interaction engine 120 sothat merchant can reliably confirm the identity of the buyer during thecard-present transaction to prevent credit fraud.

In the example of FIG. 1, user database 140, product database 150, andtransaction database 160 can be used to store information of buyer andthe merchant, products and services provided by the merchant, andtransactions performed, respectively. Here, user information (e.g.,name, telephone number, e-mail, etc.) can be obtained through onlineuser registration and product information can be provided by themerchant, while transaction database 160 is updated every time atransaction is processed by the transaction engine 130. Informationstored can be selectively accessed and provided to the buyer and/ormerchant as necessary.

In the example of FIG. 1, transaction engine 130 communicates andinteracts with the third party financial institution, user database 140,product database 150, and transaction database 160 over a network (notshown). Here, the network can be a communication network based oncertain communication protocols, such as TCP/IP protocol. Such networkcan be but is not limited to, internet, intranet, wide area network(WAN), local area network (LAN), wireless network, Bluetooth, WiFi, andmobile communication network. The physical connections of the networkand the communication protocols are well known to those of skill in theart.

Dynamic Receipt

In various embodiments, upon the completion of a financial transactionthrough, for a non-limiting example, card reader 10 connected to mobiledevice 100 associated with a merchant, transaction engine 130 running onthe mobile device 100 can be configured to capture additional dataassociated with the transaction and incorporate the additional data intoa dynamic receipt for the transaction, wherein in addition totransaction information typically included in a conventional receipt,the dynamic receipt may also include additional environmentalinformation of the transaction. For non-limiting examples, the financialtransaction can be an electronic transaction conducted over the Internetor a card present point-of-sale transaction where the buyer/payer makesthe purchase at a store front, other “brick-and-mortar” location, orsimply in presence of a merchant/payee.

In some embodiments, the additional environmental information includedin the dynamic receipt may include information pertaining to thetransaction environment. In one non-limiting example, a mobile deviceequipped with a Global Positioning System (GPS) receiver can be used tocapture the coordinates/location of the transaction, and record it as apart of the information on the dynamic receipt. This way, the physicallocation of the point of sale (which may be different from themerchant/payee's registered address) can be recorded and used bytransaction engine 120 to verify the transaction. In anothernon-limiting example, a mobile device equipped with a camera and/oraudio and/or video recorder can be used to capture a photo and/or avideo and/or an audio recording of the product or service involved inthe transaction and incorporate such data or link/reference to such datainto the dynamic receipt. In another non-limiting example, a mobiledevice with a biometric scanner can be used to scan the fingerprint orpalm print of the buyer/payer and/or merchant/payee and includes atleast a portion of such information in the dynamic receipt. In anothernon-limiting example, the mobile device can record certain informationassociated with the transaction in the dynamic receipt, wherein suchinformation includes but is not limited to, how quickly the buyer swipesthe card, the angle at which the card is swiped. In another non-limitingexample, special characteristics of the card being swiped, also referredto as the magnetic fingerprint of the card, can be recorded and includedin the dynamic receipt.

In some embodiments, the dynamic receipt can be in electronic form thatcan be accessed electronically or online and may also include link orreference pointing to multimedia information such as image, video oraudio that are relevant to the transaction.

In some embodiments, transaction engine 130 can use the environmentalinformation included in the dynamic receipt to assess risk associatedwith a transaction. For a non-limiting example, if the GPS informationindicates that the transaction is taking place in a high crime/high riskarea, the risk associated with the transaction is adjusted accordingly,and the buyer's bank may be notified accordingly. Alternatively,biometric information scanned and included in the dynamic receipt can beused for identity verification purposes to prevent identity theft andcredit fraud.

In some embodiments, transaction engine 130 can use the dynamic receiptcan be used as a non-intrusive way to communicate with the buyer and/orthe merchant. For a non-limiting example, the additional informationincluded in the dynamic receipt can be used to make offers to the buyer.If a dynamic receipt includes the GPS location of the point of sale ofthe transaction, coupons or other promotional offers made by vendors atnearby locations can be presented to the buyer when the buyer chooses toview the receipt electronically online. Alternatively, if a specificproduct involved the transaction can be identified by the transactionengine either directly through product description or indirectly byanalyzing pictures or videos taken, offers of similar or complementaryproducts can be made by a vendor to the merchant of the product.

In some embodiments, transaction engine 130 may notify buyer and/or themerchant of the receipt via an electronic message, which can be but isnot limited to, an email message, a Short Message Service (SMS) message,Twitter® (online social networking service), or other forms ofelectronic communication. The recipient of the electronic message maythen retrieve a complete itemized dynamic receipt online at his/herconvenience via a telephone number on his/her record in user database140 to retrieve his/her electronic receipts stored in transactiondatabase 160. In some embodiments, the electronic message may include anindication such as a code that the recipient can use to retrieve theelectronic receipt online as an alternative or in combination with thetelephone number.

FIG. 15 depicts a flowchart of an example of a process to supportfinancial transaction between a payer and a payee through a miniaturizedcard reader connected to a mobile device. In the example of FIG. 15, theflowchart 1500 starts at block 1502 where an amount of a financialtransaction is provided through an interactive user application launchedon the mobile device as shown in FIG. 16A. The flowchart 1500 continuesto block 1504 where a miniaturized card reader structured to minimizeswipe error is connected to the mobile device as shown in FIG. 16B. Theflowchart 1500 continues to block 1506 where a card is swiped throughthe card reader to initiate the financial transaction as shown in FIG.16C. The flowchart 1500 continues to block 1508 where the payer confirmsthe amount of the card-present transaction via a signature signed viathe interactive user application on the mobile device to complete thetransaction as shown in FIG. 16D. Note that the signature is required asan additional layer of confirmation for the protection for the payereven when such signature may not be technically required to authorizethe transaction. The flowchart 1500 continues to block 1510 where resultof the transaction is received and presented to the payer and/ormerchant as shown in FIG. 16E. The flowchart 1500 ends at block 1512where an electronic receipt of the transaction is provided to the payerin the form of an electronic message as shown in FIG. 16F.

The foregoing description of various embodiments of the claimed subjectmatter has been provided for the purposes of illustration anddescription. It is not intended to be exhaustive or to limit the claimedsubject matter to the precise forms disclosed. Many modifications andvariations will be apparent to the practitioner skilled in the art.Particularly, while the concept “component” is used in the embodimentsof the systems and methods described above, it will be evident that suchconcept can be interchangeably used with equivalent concepts such as,class, method, type, interface, module, object model, and other suitableconcepts. Embodiments were chosen and described in order to bestdescribe the principles of the invention and its practical application,thereby enabling others skilled in the relevant art to understand theclaimed subject matter, the various embodiments and with variousmodifications that are suited to the particular use contemplated.

1-20. (canceled)
 21. A method for automatic storage of electronicreceipts and subsequent retrial of the electronic receipts, the methodcomprising: acquiring, by a transaction engine, transaction informationabout a first transaction from a first merchant and a second transactionfrom a second merchant, the transaction information from the firstmerchant and the second merchant both including a transaction cardnumber for a transaction card, wherein the transaction engine isunrelated to a card issuer; automatically storing the transactioninformation about the first transaction and the second transaction aselectronic receipts in a transaction database in association with anidentifier associated with the transaction card in a user database;receiving, by the transaction database, a request from a user device forat least one of the electronic receipts associated with the identifier;and presenting the at least one of the electronic receipts associatedwith the identifier to the user device.
 22. The method of claim 21,wherein the first transaction is associated with a first transactioncard, and the second transaction is associated with a second transactioncard, and wherein the identifier is associated with both the firsttransaction card and the second transaction card.
 23. The method ofclaim 21, comprising: after acquiring the transaction information foreither of the first transaction or the second transaction, sending anotification to a phone number associated with the transaction card inthe user database, the notification indicating that a respective one ofthe first transaction or the second transaction has been completed andindicating that the electronic receipt is ready to be retrieved.
 24. Themethod of claim 23, wherein the notification including data to retrievethe electronic receipt from the transaction database.
 25. The method ofclaim 21, wherein the transaction information further includes alocation in which the first transaction or second transaction tookplace, and wherein the location is included with the transactioninformation on the at least one of the electronic receipts.
 26. Themethod of claim 21, wherein the transaction information further includesa transaction result of the first transaction or the second transaction,the transaction result being received from a server of the card issuer.27. The method of claim 25, further comprising: prior to the presentingthe at least one of the electronic receipts associated with theidentifier to the user device, retrieving at least one data item that isprovided by a server separate from the transaction engine; and includingthe at least one data item as part of the electronic receipt.
 28. Themethod of claim 27, wherein the at least one data item is anadvertisement for a vendor nearby the location in which the firsttransaction or second transaction took place.
 29. The method of claim21, wherein the transaction information further includes biometric dataassociated with a user of the transaction card, and wherein theelectronic receipt includes at least a portion of the biometric data.30. A system for automatically storing electronic receipts andsubsequently retrieving the electronic receipts, comprising: a userdatabase to store a relationship between a transaction card of a userand a phone number or email account associated with the user; atransactions database to store transaction information pertaining totransactions from a plurality of merchants; a transaction engine that isconfigured to: process transactions originating from merchants receivingrespective user's transaction cards issued from respective institutionsthat are a third party with respect to the transaction engine, whereininformation about each of the processed transactions is the transactioninformation, and automatically store the transaction information in thetransaction database in association with the phone number or emailaccount associated with the transaction card in the user database; thetransactions database configured to: receive, a request from a userdevice for transaction information associated with the phone number oremail account, and present the transaction information associated withthe phone number or email account to the user device.
 31. The system ofclaim 30, wherein the transactions database stores transactioninformation for first transaction associated with a first transactioncard, and a second transaction associated with a second transactioncard, and wherein the phone number or email account is associated withboth the first transaction card and the second transaction card.
 32. Thesystem of claim 30, wherein the transaction engine is further configuredto: send a notification to the phone number or email account associatedwith the transaction card in the user database, the notificationindicating that a first transaction has been completed and indicate thatan electronic receipt is ready to be retrieved.
 33. The system of claim32, wherein the notification including data to retrieve the electronicreceipt from the transaction database.
 34. The system of claim 30,wherein the transaction information further includes a location in whicha first transaction took place, and the transaction information furtherincludes a location in which the first transaction or second transactiontook place, and prior to the presentation of the transactioninformation, retrieve at least one data item that is provided by aserver separate from the transaction engine or the transactionsdatabase, and include the at least one data item with the transactioninformation.
 36. A non-transitory computer readable medium comprisinginstructions, the instructions, when executed by a computing system,cause the computing system to: automatically store transactioninformation about a first transaction in which a first transaction cardwas utilized as an electronic receipt in a transaction database inassociation with a identifier associated with the transaction card in auser database, wherein the transaction database stores informationregarding transactions from a plurality of merchants, and utilizing aplurality of transaction cards from different card issuers, thetransaction database being a third party with respect to the cardissuers and plurality of merchants; receive a request from a user devicefor the electronic receipt associated with the identifier; and presentthe electronic receipt associated with the identifier to the userdevice.
 37. The non-transitory computer readable medium of claim 36,wherein the request for the electronic receipt is a request for aplurality of electronic receipts associated with a phone number as theidentifier.
 38. The non-transitory computer readable medium of claim 37,wherein the phone number is associated with a plurality of transactioncards, and the plurality of electronic receipts are associated with oneor both of the plurality of transaction cards.
 39. The non-transitorycomputer readable medium of claim 36, wherein the computer readablemedium further comprises instructions that, when executed by thecomputing system, cause the computing system to: send a notification toa phone number or email address associated with the transaction card inthe user database, the notification indicating that the electronicreceipt is ready to be retrieved.
 40. The computer readable medium ofclaim 36, wherein the transaction information further includes biometricdata associated with a user of the transaction card, and wherein theelectronic receipt includes at least a portion of the biometric data.